System and method for merging remote and local data in a single user interface

ABSTRACT

The system comprises a local database; a user interface; a remote access engine, communicatively coupled to a network, the user interface, and the local database; and a rendering engine, communicatively coupled to the remote access engine. The user interface receives a data search request. The remote access engine searches for and retrieves, from a remote database communicatively coupled to the network and the local database, data corresponding to the received search request. The rendering engine displays the received data from the remote database and the local database.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.10/279,369, filed Oct. 23, 2002, and is based upon and claims benefit ofpatent application No. 60/336,444, entitled “System And Method ForMerging Remote And Local Data In A Single User Interface,” filed on Oct.23, 2001, by inventor Daniel Mendez. The entire contents of each ofwhich are incorporated herein by reference.

BACKGROUND

1. Field of the Invention

This invention relates generally to user interfaces, and moreparticularly, but not exclusively, provides a system and method formerging remotely and locally stored data into a single user interface.

2. Discussion of the Background

Conventionally, wireless devices, such as wireless-enabled PDAs, enablea user to search for, retrieve, and display locally stored data.Further, wireless devices may also enable a user to search for,retrieve, and display remotely stored data. However, even if searchterms are identical for searching from locally stored and remotelystored data, each search must be performed separately, and results mustbe displayed separately.

Accordingly, a new system and method for searching, retrieving, anddisplaying locally and remotely stored data are needed.

SUMMARY OF THE INVENTION

The present invention provides a system for merging remotely and locallystored data into a single user interface. The system comprises a remoteaccess client; a browser/rendering client; an application/user interface(UI); and a local database. The remote access client enables the systemto access remotely stored data. The browser/rendering client renders adisplay on a monitor or other display device. The application/userinterface receives data search requests and enables a user to refinedata search requests. Further, the application/user interface, inconjunction with the remote access engine, accesses remotely stored datato receive data corresponding to the search request. Theapplication/user interface also accesses the local database to retrievelocally stored data corresponding to the search request. Theapplication/user interface, in conjunction with the browser/renderingclient, then displays the matching data from the database and from theremotely stored data in a merged interface.

The present invention further provides a method for merging remotely andlocally stored data into a single user interface. The method comprises:receiving a data search request, searching locally stored and remotelystored data for data corresponding to the data search request;retrieving data corresponding to the data search request from locallyand remotely stored data, and displaying the retrieved data from locallystored and remotely stored locations corresponding to the data searchrequest in a merged user interface.

Accordingly, the system and method may advantageously merge remotely andlocally stored data into a single user interface.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the present invention aredescribed with reference to the following figures, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified.

FIG. 1 is a block diagram illustrating a network system in accordancewith an embodiment of the present invention;

FIG. 2 is a block diagram illustrating an example computer in accordancewith an embodiment of the present invention;

FIG. 3 is a block diagram illustrating details of the integrated userinterface system of FIG. 1;

FIG. 4 is a flowchart illustrating a method for viewing data storedeither locally or remotely FIG. 5 is a flowchart illustrating a methodfor merging remotely and locally stored data into a single userinterface;

FIG. 6 is a diagram illustrating an example embodiment of a userinterface selection page;

FIG. 7 is a diagram illustrating a corporate directory graphical userinterface for searching and retrieving data from a local memory, aremote memory and merged memory (i.e., both local and remote memory);

FIG. 8 is a diagram illustrating a search term page for retrieving datafrom both local and remote memory for display in a single interface;

FIG. 9 is a diagram illustrating a refine search page; and

FIG. 10 is a diagram illustrating local and remote corporate data mergedinto an example single user interface.

DESCRIPTION OF THE EMBODIMENTS

The following description is provided to enable any person skilled inthe art to make and use the invention, and is provided in the context ofa particular application and its requirements. Various modifications tothe embodiments will be readily apparent to those skilled in the art,and the generic principles defined herein may be applied to otherembodiments and applications without departing from the spirit and scopeof the invention. Thus, the present invention is not intended to belimited to the embodiments shown, but is to be accorded the widest scopeconsistent with the principles, features and teachings disclosed herein.

FIG. 1 is a block diagram illustrating a mobile device 150, and remoteserver computer(s) 130 communicatively coupled to a network 140, such asthe Internet or a LAN, etc. In an embodiment of the invention, remoteserver computer(s) may be behind a firewall. The remote servercomputer(s) 130 is communicatively coupled to remote storage 100. Mobiledevice 150 may include a personal digital assistant (PDA), laptopcomputer, mobile phone or any other device capable to communicate withremote server computer(s) 130. Further, mobile device 150, as well asremote server computer(s) 130, may be communicatively coupled to network140 via a wired or wireless connection. In an alternative embodiment,mobile device 150 may be directly communicatively coupled to remoteserver computer(s) 130 without the use of network 140. Mobile device 150will be discussed in further detail in conjunction with FIG. 2.

Remote server computer(s) 130 includes a synchronization server 140 anda remote access (R/A) server 145. Synchronization server 140synchronizes sync W/E 127 in remote database 120 with data stored inmobile device 150.

Remote storage device 100 may include a server or other device forstoring data and is capable to communicate with remote servercomputer(s) 130. Remote storage 100 includes a remote database manager110 and a remote database 120. Remote database manager 110 managesdatabase 120, which includes remote workspace elements (W/E) 125 andsync W/E 127. Remote W/E 125 includes data that is stored remotely andnot synchronized with data stored in mobile device 150. Sync W/E 127includes data that is stored remotely and also synchronized with datastored in mobile device 150. In general, remote database 120 may includecorporate data, such as a corporate directory, corporate schedules,sales force automation (SFA) data, and/or customer relationshipmanagement (CRM) data, etc. As compared with database 340 (FIG. 3) ofmobile device 150, remote database 120 generally may include informationthat is sensitive, voluminous, and/or quickly stale. R/A server 145enables mobile device 150 to remotely log into remote storage 100 andaccess remote database 120 to search for and retrieve data.

FIG. 2 is a block diagram illustrating an example computer in accordancewith the present invention. In an embodiment of the invention, mobiledevice 150 and remote server computer(s) 130 may include or be residenton a computer that is substantially similar to example computer 200. Theexample computer 200 includes a central processing unit (CPU) 205;working memory 210; persistent memory 220; input/output (I/O) interface230; display 240 and input device 250, all communicatively coupled toeach other via system bus 260. CPU 205 may include an Intel Pentium.RTM.microprocessor, a Motorola PowerPC.RTM. microprocessor, or any otherprocessor capable to execute software stored in persistent memory 220.Working memory 210 may include random access memory (RAM) or any othertype of read/write memory devices or combination of memory devices.Persistent memory 220 may include a hard drive, read only memory (ROM)or any other type of memory device or combination of memory devices thatcan retain data after example computer 200 is shut off. I/O interface230 is communicatively coupled, via wired or wireless techniques, tonetwork 140. In an alternative embodiment of the invention, I/O 230 maybe directly communicatively coupled to a server or computer, therebyeliminating the need for network 140. Display 240 may include a cathoderay tube display or other display device. Input device 250 may include akeyboard, mouse, or other device for inputting data, or a combination ofdevices for inputting data.

One skilled in the art will recognize that the example computer 200 mayalso include additional devices, such as network connections, additionalmemory, additional processors, LANs, input/output lines for transferringinformation across a hardware channel, the Internet or an intranet, etc.One skilled in the art will also recognize that the programs and datamay be received by and stored in the system in alternative ways.

FIG. 3 is a block diagram illustrating integrated UI system 160 of themobile device 150. System 160 includes a remote access client 300, abrowser/rendering client 310, a sync client 320, an application/UI 330,and a database 340. Remote access client 300 accesses remote database120 (FIG. 1) for searching, modifying and/or retrieving data.Browser/rendering client 310 renders data so as to be viewable ondisplay 240. Sync client 320, in conjunction with remote access client300, synchronizes data stored in database 340 with data stored in remotedatabase 120.

Note that not all data in database 340 is synchronized with remotedatabase 120. Conversely, not all data in remote database 120 issynchronized with database 340. For example, remote W/E 125 in remotedatabase 120, which may be deemed to be sensitive, voluminous or quicklygoes stale, will not be synchronized with database 340 because themobile device may be easily lost or stolen, may contain limited memoryfor storing data, may have limited bandwidth to transfer large amountsof data, and/or for other reasons. Also note that not all data indatabase 340 will be synchronized with remote database 120 because someof the data in database 340 may be private, personal, and/or for otherreasons. Alternatively, data in database 340 may be synchronized with asecond remote storage device (not shown).

Application/UI 330 includes a client capable to accept data searchrequests from a user and to refine those requests. Further,application/UI 330 searches local database 340 and, in conjunction withremote access client 300, queries remote database manager 110 to searchremote database 120 for data corresponding to the data search requestsand retrieves the corresponding data. Application/UI 330, in conjunctionwith browser/rendering client 310, can display the retrieved data in amerged user interface on a display, such as display 240.

Application/UI 330 may include a single user interface application ormay include a plurality of user interface applications. For example, inan embodiment of the invention, application/UI 330 may include acorporate directory UI capable to search, retrieve, and displaycorporate directory workspace elements from remote database 120 anddatabase 340 in a single merged UI. In another embodiment of theinvention, application/UI 330 may include a calendar UI capable tosearch, retrieve, and display calendar workspace elements from remotedatabase 120 and database 340 into a single merged display. Otherembodiments of application/UI 340 include a customer relationshipmanagement (CRM) interface, a sales force automation (SFA) interface, atasks interface, and a files interface.

FIG. 4 is a flowchart illustrating a method 400 for viewing data storedeither locally or remotely. In an embodiment of the invention,application/UI 330, in conjunction with remote access client 300 andbrowser/rendering client 310, perform the method 400. First, a datarequest is received (405) from a user via a data input device, such asinput device 250, of a device, such as mobile device 150. The datarequest may include a type of data to search for (e.g., CRM, SFA,corporate directory data, calendar data, etc.), search terms, andwhether to search a remote database, a local database, or both local andremote (i.e., merged) databases. Next, it is determined (410) if thedata request is for merged data (i.e., search both local and remotedatabases). If the data request is for merged data, then a number ofworkspace elements in local and remote databases matching the searchterms is identified (510, FIG. 5) as will be discussed further below inconjunction with FIG. 5.

If the data request does not specify searching both remote and localdatabases, then it is determined (420) if the data request is for aremote database only. If the data request is not for a remote database,then the data request is for a local database and a number of workspaceelements in a local database, such as database 340, matching the searchterms is identified (450), as will be discussed further below.

If data request is for a remote database, then a number of workspaceelements in a remote database, such as remote database 120, that matchthe search request terms is identified (425). It is then determined(430) if the number of matching workspace elements is voluminous, e.g.,more than can be displayed simultaneously on a display, such as display240, or more than a pre-specified number, etc. If the number ofworkspace elements is determined to be voluminous, then search terms inthe data request are refined (435) per a user's specifications or viaother techniques. The number of workspace elements matching the refinedsearch terms is then identified (425). This process of refining searchterms is repeated until the number of workspace elements is determinednot to be voluminous.

After the number of workspace elements having matching search terms hasbeen determined not to be voluminous, then the matching workspaceelements are retrieved (440) from the remote database. The retrievedworkspace elements are then displayed (445) on display device, such asdisplay 240. In another embodiment of the invention, the retrievedworkspace elements or a subset of retrieved workspace elements may thenalso be stored in local memory. The method 400 then ends.

If it is determined that the search request is not for a remotedatabase, as discussed above, then, a number of workspace elements in alocal database matching the search terms in the request is identified(450). It is then determined (455) if the number of matching workspaceelements in the local database is voluminous, e.g., more than can bedisplayed simultaneously on a display, such as display 240, or more thana pre-specified number, etc. If the number of workspace elements isdetermined to be voluminous, then search terms in the data request arerefined (460) per a user's specifications or via other techniques. Thenumber of workspace elements matching the refined search terms is thenidentified (450). This process of refining search terms is repeateduntil the number of workspace elements is determined not to bevoluminous.

After the number of workspace elements having matching search terms hasbeen determined not to be voluminous, then the matching workspaceelements are retrieved (465) from the local database. The retrievedworkspace elements are then displayed (470) on a display device, such asdisplay 240. The method 400 then ends.

FIG. 5 is a flowchart illustrating a method 500 for merging remotely andlocally stored data into a single user interface. In an embodiment ofthe invention, application/UI 330 in conjunction with remote accessclient 300 and browser/rendering client 310, perform the method 500.After receiving (405; FIG. 4) a data request and determining (410) thatthe data request is for workspace elements from both a local and aremote database, a number of workspace elements in the local and theremote databases matching the data request is determined (510). It isthen determined (520) if the number of matching workspace elements isvoluminous, e.g., more than can be displayed simultaneously on adisplay, such as display 240, or more than a pre-specified number, etc.If the number of workspace elements is determined to be voluminous, thensearch terms in the data request are refined (530) per a user'sspecifications or via other techniques. The number of workspace elementsmatching the refined search terms is then identified (510). This processof refining search terms is repeated until the number of workspaceelements is determined not to be voluminous.

After the number of workspace elements having matching search terms hasbeen determined not to be voluminous, then the matching workspaceelements are retrieved (540) from the remote database. The retrievedworkspace elements from both local and remote databases are thendisplayed (550) on display device, such as display 240. In anotherembodiment of the invention, the retrieved workspace elements or asubset of retrieved workspace elements from the remote database may thenalso be stored in the local database. Further, the retrieved workspaceelements or a subset of retrieved workspace elements from the localdatabase may then also be stored in the remote database. The method 500then ends.

FIG. 6 is a diagram illustrating an example embodiment of a userinterface selection page. The page enables a user to select one of n,e.g., six user interfaces for retrieving data from remote and/or localmemory. The user interfaces include a calendar 610, directory 620, tasks630, files 640, SFA 650 and CRM 660. In another embodiment of theinvention, additional or alternative UIs may be available.

FIG. 7 is a diagram illustrating a corporate directory graphical userinterface for searching and retrieving data from a local database, aremote database and merged databases (i.e., both local and remotedatabases). Options for searching and retrieving data include a firstoption 710 to enable a user to retrieve data from a local database, asecond option 720 to retrieve data from a remote database, and a thirdoption 730 for retrieving data from both local and remote databases.

FIG. 8 is a diagram illustrating a search term page for retrieving datafrom both local and remote databases for display in a single interface.Search options include a first option 810 to show workspace elements inalphabetical order starting with a letter selected by a user viaentering the desired letter; a second option 820 to show workspaceelements based on having a specific name; a third option 830 forentering search terms; and fourth option 840 to show directory workspaceelements in alphabetic order starting with a letter as selected by auser pressing a button corresponding to the letter. Other methods ofsearching and retrieving workspace elements may also be incorporatedinto the search term page including a Boolean terms search, etc.

FIG. 9 is a diagram illustrating a refine search page. If the searchperformed returns a number of workspace elements determined to bevoluminous, e.g. too many workspace elements to be displayedsimultaneously, etc. then the number of matching workspace elements mustbe pared down. Options for refining the search include a first option910 to only display the first five matching workspace elements; a secondoption 920 to display the last five matches; and a third option 930 tosearch the matching workspace elements using user-specified searchterms. In an embodiment of the invention, other techniques for refine asearch may also be included.

FIG. 10 is a diagram illustrating local and remote corporate directorydata merged into an example single user interface. The interfacedisplays workspace elements 1010, which for each workspace elementincludes an employee name, an email address, and a store indicatingwhere the workspace element is stored, i.e., local or remote. Forexample, employee Aaron has an email address of aaron@abc.com and his orher workspace element is stored in remote memory. In comparison,employee Andrews has an email address of Andrews@abc.com and his or herworkspace element is stored in local memory. In an alternativeembodiment, workspace elements may display additional or alternativedata, such as home, work, facsimile and/or mobile phone numbers, emailaddresses, employee photos, employee identification numbers, employeejob skills, languages spoken by employees, employee job positions ortitles, employee educational backgrounds, corporate location, etc. Inaddition, workspace elements 1010 may include data workspace elementsfor corporations, corporate subdivisions, and other entities.

In addition to the workspace elements 1010, the interface of FIG. 10also has buttons 1020 for performing functions including: adding a newworkspace element to a local database; delete a workspace element fromlocal or remote databases (in one embodiment, a user may only be able todelete a workspace element from a local database); add a workspaceelement stored remotely, such as workspace element 1010 a, to a localdatabase or add a workspace element stored locally, such as workspaceelement 1101 d, to a remote database; display a first page of workspaceelements according to search parameters defined earlier; display a nextpage of workspace elements according to search parameters definedearlier; displaying a previous page of workspace elements according tosearch parameters defined earlier; and displaying a last page ofworkspace elements according to search parameters defined earlier. In analternative embodiment of the invention, other features may beinstituted in addition or in alternative to the features enabled bybuttons 1020.

The foregoing description of the preferred embodiments of the presentinvention is by way of example only, and other variations andmodifications of the above-described embodiments and methods arepossible in light of the foregoing teaching. Although the network sitesare being described as separate and distinct sites, one skilled in theart will recognize that these sites may be a part of an integral site,may each include portions of multiple sites, or may include combinationsof single and multiple sites on either side of a firewall. Further,components of this invention may be implemented using a programmedgeneral purpose digital computer, using application specific integratedcircuits, or using a network of interconnected conventional componentsand circuits. Connections may be wired, wireless, modem, etc. Theembodiments described herein are not intended to be exhaustive orlimiting. The present invention is limited only by the following claims.

1. A method, comprising: receiving a data search request specifying atleast one database to search for data; searching in a local database,upon indication that the local database is included in the at least onedatabase specified in the data search request, for each data entry inthe local database fulfilling requirements of the data search request;querying via a wireless connection a remote database manager to searchin a remote database, upon indication that the remote database isincluded in the at least one database specified in the data searchrequest, for each data entry in the remote database fulfilling therequirements of the data search request; determining if receiving thedata corresponding to the data search request would exceed a thresholdof an amount of data that can be displayed simultaneously on a displayof a handheld device; refining the data search request if thedetermining indicates that receiving the data corresponding to the datasearch request would exceed the threshold; retrieving, from the localdatabase, data entries found in the searching fulfilling therequirements of the data search request; receiving, from the remotedatabase via the wireless connection, data entries found in the queryingfulfilling the requirements of the data search request; and merging theretrieved and received data entries.
 2. The method of claim 1, furthercomprising: excluding voluminous data exceeding a threshold, thevoluminous data stored in the remote database, from the received datacorresponding to the received data request.
 3. The method of claim 1,further comprising: excluding confidential data, stored in the remotedatabase, from the received data corresponding to the received datarequest.
 4. The method of claim 1, further comprising: excludingobsolete data that is stored in the remote database longer than athreshold time period from the received data corresponding to thereceived data request.
 5. The method of claim 1, further comprising:excluding personal data associated with a user, the personal data storedin the local database, from the received data corresponding to thereceived data request.
 6. The method of claim 1, wherein the local andremote databases store sales force automation data.
 7. The method ofclaim 1, wherein the local and remote databases store customer relationsmanagement data.
 8. The method of claim 1, wherein the local and remotedatabases store corporate directory data.
 9. The method of claim 1,wherein the local and remote databases store calendar data.
 10. Themethod of claim 1, wherein the local and remote databases store tasksdata.
 11. The method of claim 1, wherein the local and remote databasesstore files.
 12. The method of claim 1, further comprising: saving, tothe local database, the data received from the remote database.
 13. Themethod of claim 1, wherein the local database is data stored on asmartphone.
 14. The method of claim 1, wherein the remote database isdata stored on a remote personal computer.
 15. The method of claim 1,further comprising: accessing the remote database using a one port of aplurality of ports on a firewall; and presenting in a single userinterface that the retrieved data is stored in the local database, andthe received data is stored in the remote database.
 16. The method ofclaim 1, wherein searching the local database and querying the remotedatabase manager are performed in response to the sole data searchrequest.
 17. A computer readable medium, including computer executableinstructions that cause a computer to implement a method comprising:receiving a data search request specifying at least one database tosearch for data; searching in a local database, upon indication that thelocal database is included in the at least one database specified in thedata search request, for each data entry in the local databasefulfilling requirements of the data search request; querying via awireless connection a remote database manager to search in a remotedatabase, upon indication that the remote database is included in the atleast one database specified in the data search request, for each dataentry in the remote database fulfilling the requirements of the datasearch request; determining if receiving the data corresponding to thedata search request would exceed a threshold of an amount of data thatcan be displayed simultaneously on a display of a handheld device;refining the data search request if the determining indicates thatreceiving the data corresponding to the data search request would exceedthe threshold; retrieving, from the local database, data entries foundin the searching fulfilling the requirements of the data search request;receiving, from the remote database via the wireless connection, dataentries found in the querying fulfilling the requirements of the datasearch request; and merging the retrieved and received data entries. 18.The computer readable medium of claim 17, further comprising: excludingvoluminous data exceeding a threshold, the voluminous data stored in theremote database, from the received data corresponding to the receiveddata request.
 19. The computer readable medium of claim 17, furthercomprising: excluding confidential data, stored in the remote database,from the received data corresponding to the received data request. 20.The computer readable medium of claim 17, further comprising: excludingobsolete data that is stored in the remote database longer than athreshold time period from the received data corresponding to thereceived data request.
 21. The computer readable medium of claim 17,further comprising: excluding personal data associated with a user, thepersonal data stored in the local database, from the received datacorresponding to the received data request.
 22. The computer readablemedium of claim 17, wherein the local and remote databases store salesforce automation data.
 23. The computer readable medium of claim 17,wherein the local and remote databases store customer relationsmanagement data.
 24. The computer readable medium of claim 17, whereinthe local and remote databases store corporate directory data.
 25. Thecomputer readable medium of claim 17, wherein the local and remotedatabases store calendar data.
 26. The computer readable medium of claim17, wherein the local and remote databases store tasks data.
 27. Thecomputer readable medium of claim 17, wherein the local and remotedatabases store files.
 28. The computer readable medium of claim 17,wherein the method further comprises: saving, to the local database,data received from the remote database.
 29. The computer readable mediumof claim 17, wherein the local database is data stored on a smartphone.30. The computer readable medium of claim 17, wherein the remotedatabase is data stored on a remote personal computer.
 31. The computerreadable medium of claim 17, wherein searching the local database andquerying the remote database manager are performed in response to thesole data search request.
 32. The computer readable medium of claim 17,wherein the method further comprises: accessing the remote databaseusing port one of a plurality of ports on a firewall, and presenting ina single user interface that the retrieved data is stored in the localdatabase, and the received data is stored in the remote database.
 33. Asystem, comprising: means for receiving a data search request specifyingat least one database to search for data; means for searching in a localdatabase, upon indication that the local database is included in the atleast one database specified in the data search request, for each dataentry in the local database fulfilling requirements of the data searchrequest; means for querying via a wireless connection a remote databasemanager to search in a remote database, upon indication that the remotedatabase is included in the at least one database specified in the datasearch request, for each data entry in the remote database fulfillingthe requirements of the data search request; means for determining ifreceiving the data corresponding to the data search request would exceeda threshold of an amount of data that can be displayed simultaneously ona display of a handheld device; means for refining the data searchrequest if the determining indicates that receiving the datacorresponding to the data search request would exceed the threshold;means for retrieving, from the local database, data entries found by themeans for searching fulfilling the requirements of the data searchrequest; means for receiving, from the remote database via the wirelessconnection, data entries found by the means for querying fulfilling therequirements of the data search request; and means for merging theretrieved and received data entries.
 34. The system of claim 33, furthercomprising: a firewall to protect the remote database, wherein the meansfor presenting the retrieved and received data in the single userinterface also presents in the single user interface that the retrieveddata is stored in the local database, and the received data is stored inthe remote database.
 35. The system of claim 33, wherein the means forquerying the remote database manager queries the remote database managerin response to the sole data search request.
 36. A system comprising: afirewall that includes at least one port; a smartphone, outside thefirewall, that includes: a local database; a user interface engine toreceive a data search request, and to search and retrieve, from thelocal database, a first data corresponding to the data search request,and to receive from a remote database manager a second data,corresponding to the data search request, retrieved from a remotedatabase; a rendering engine to present in a single user interface thefirst data retrieved from the local database and also the second datareceived from the remote database; and a first synchronization engine tosynchronize at least a portion of data stored in the local database withcorresponding data stored in the remote database; a server, behind thefirewall, that includes: the remote database; the remote databasemanager to search and retrieve, from the remote database, the seconddata corresponding to the data search request; and a secondsynchronization engine to synchronize at least a portion of the datastored in the remote database with the corresponding data stored in thelocal database; and a communication channel to couple the server to thesmartphone using a particular one of the at least one port on thefirewall.
 37. The system of claim 36, wherein the second synchronizationengine initiates synchronization from behind the firewall.
 38. Thesystem of claim 36, wherein the single user interface specifies that thefirst data is stored in the local database, and that the second data isstored in the remote database.